Hi,
does anybody know how I can determine with dxl the name of the user who soft deleted a module
( over the years we have many soft deleted modules which have never been purged - I have a dxl
script which lists all soft deleted modules but want to know who did the deed )
Regards, Paul
SystemAdmin - Fri Jul 31 08:10:37 EDT 2009 |
|
Re: Finding user who soft deleted a module llandale - Fri Jul 31 11:01:52 EDT 2009
Oddly its not recorded in module History, no doubt because the module isn't open when you delete it. As far as I know there's no way to find out.
I'd go through History and try to figure out who did most of the edits, or who did the most recent edits.
|
|
Re: Finding user who soft deleted a module kbmurphy - Fri Jul 31 16:17:15 EDT 2009
...or you could set your security so that users can't delete modules to begin with.
|
|
Re: Finding user who soft deleted a module SystemAdmin - Mon Aug 03 02:26:31 EDT 2009 llandale - Fri Jul 31 11:01:52 EDT 2009
Oddly its not recorded in module History, no doubt because the module isn't open when you delete it. As far as I know there's no way to find out.
I'd go through History and try to figure out who did most of the edits, or who did the most recent edits.
Hi Louie,
Unfortunately the module handles for deleted modules appear to be nulls so I can't access
the module history to get the last edits etc - I use the following dxl but always get NULL for
the module handle if it's deleted
for itemRef in all folder do {
if(isDeleted(itemRef) ){
Module m = module ( itRefFolder )
if( null m ){
print"Module handle is null\n"
}
}
}
Regards, Paul
|
|
Re: Finding user who soft deleted a module llandale - Mon Aug 03 13:57:32 EDT 2009 SystemAdmin - Mon Aug 03 02:26:31 EDT 2009
Hi Louie,
Unfortunately the module handles for deleted modules appear to be nulls so I can't access
the module history to get the last edits etc - I use the following dxl but always get NULL for
the module handle if it's deleted
for itemRef in all folder do {
if(isDeleted(itemRef) ){
Module m = module ( itRefFolder )
if( null m ){
print"Module handle is null\n"
}
}
}
Regards, Paul
If you get rid of your 'isDeleted' check you will find all Module handles are null, since the 'module' function only retrieves that when a module is open. You need to open the module with perhapsm 'read(fullName(itemRef), false)', but you cannot do that because its closed. You'll have to un-delete it to open it, then re-delete it; which is counter productive to find out who deleted it originally.
I don't see anyway to do this.
|
|
Re: Finding user who soft deleted a module SystemAdmin - Tue Aug 04 08:05:56 EDT 2009 llandale - Mon Aug 03 13:57:32 EDT 2009
If you get rid of your 'isDeleted' check you will find all Module handles are null, since the 'module' function only retrieves that when a module is open. You need to open the module with perhapsm 'read(fullName(itemRef), false)', but you cannot do that because its closed. You'll have to un-delete it to open it, then re-delete it; which is counter productive to find out who deleted it originally.
I don't see anyway to do this.
Hi Louie,
thanks, will just have to mail all users warning of impending purge :-)
Paul
|
|
Re: Finding user who soft deleted a module dpechacek - Tue Aug 04 11:59:37 EDT 2009 SystemAdmin - Tue Aug 04 08:05:56 EDT 2009
Hi Louie,
thanks, will just have to mail all users warning of impending purge :-)
Paul
Set your module access rights to be RC at the module level and then propagate the rest of the access rights people need into the module. We propagate MDA into the module. Admin access only so people can create new sections(for modules where they need to). I set up specific access rights for all the attributes and types so they don't have admin access to those.
AAI Services, Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
|
|